DOOML: add compiler doing everything for A (well, we hope to add everything) by georgiy-belyanin · Pull Request #50 · Kakadu/comp25

georgiy-belyanin · 2026-01-16T16:33:25Z

This PR introduces a complete DOOML complier implementation. It was made by Georgiy Belyanin (@georgiy-belyanin) and Ignat Sergeev (@IgnatSergeev).

What features were implemented?

This is quasi-initial commit of the DOOML language compiler done in terms of functional language compilers 2025 SPbU course. Basically, it is OCaml-like language with (drastically) truncated list of features. This patch introduces a basic AST and parser with pretty-printing facilities. Only integers, units and tuples are supported yet. This will be implemented by Georgiy Belyanin and Ignatiy Sergeev.

This patch introduces a-normal-form (ANF) as a step in the compiler's middle-end. ANF is responsible to make the function calls only contain variables or immediate values as their arguments which makes the code kind of resemble assembly in the sense that assembler instructions usually work with registers/immediate values not with compound statements. Example: ```ocaml (* Before ANF *) let f = let q = f ((g + sup0) * (2 * i)) in q ;; (* After ANF *) let f = let sup2 = (*) 2 i in let sup5 = (+) g sup0 in let sup6 = (*) sup5 sup2 in let sup7 = (f) sup6 in let q = sup7 in q ;; ```

This patch fixes AST pretty-printing by properly using format boxes. It is relatively hard to describe what has changed since the previous usage was completely wrong. Let's provide a few examples instead to notice the difference between the old formatting and the new one. Old: ``` let a = 15 in let b = 4 in let c = 8 in ... ``` New: ``` let a = 15 in let b = 4 in let c = 8 in ... ``` Old: ``` let smth = if long_cond then long_one else long_two in ``` New: ``` let smth = if long_cond then long_one else long_two in ```

Previous implementation of the if-then-else ANF process was wrong. It actually executed both then and else branches and then chosen one of the results. This patch fixes it and now both branches are executed exclusively.

This patch prevents the parser from handling the keywords as identifiers.

This patch introduces plugs, tuples, and units into the parser. In other words, the following code can now be parsed properly. ```ocaml let () = _;; let _ = _;; let (a, b) = _;; ```

This patch fixes the if-then-else (ite) condition parsing. The problem was that it was impossible to use ite inside ite conditions (for some unknown reason). The problem could be fixed by removing a few parser-combinator commits. Let's do it even though it would make errors less useful. Actually, the patch improves pretty-printing too.

This patch significantly improves the ANF stage. It does the following. * It makes ANF accept the whole program as input. * It improves pretty-printing (similarly to AST in the previous patch). * It allows to ANF tuples as follows. Before ANF. ``` let (a, b) = c;; ``` After ANF. ``` let a = nth c 0;; let b = nth c 1;; ``` It also makes it internally use a state monad.

This patch introduces basic closure-conversion and lambda-lifting allowing DOOML to handle closures. They are usually used together so they are added in a single patch. ```ocaml let f = fun a c -> let g = fun b -> a + b in g c ;; (* CC turns it into... *) let f = fun a c -> let g = (fun a b -> a + b) a in g c ;; (* LL turns it into... *) let g = (fun a b -> a + b) a;; let f = fun a c -> g c ;; ```

This patch introduces basic DOOML compilation into RISC-V assembly, namely rv64gc. The patch does not yet verify it. However, a few tests are about to be added soon. Additionally, there is C runtime. It must be compiled by cross-toolchain and linked across the generated assembly in order for everything to work properly.

separate

Let's try to cleanup everything...

github-actions

Zanuda-linter report

github-actions · 2026-03-15T19:56:06Z

DOOML/lib/fe.ml

@@ -0,0 +1,431 @@
+open Angstrom


File 'DOOML/lib/fe.ml' doesn't have corresponding .mli interface

github-actions · 2026-03-15T19:56:06Z

DOOML/bin/llvm.ml

+open DOOML
+module Map = Base.Map.Poly
+
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T19:56:06Z

DOOML/bin/riscv.ml

+open DOOML
+module Map = Base.Map.Poly
+
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T19:56:06Z

DOOML/lib/anf.ml

@@ -0,0 +1,427 @@
+type immexpr =


OCaml files should provide license information in second line (structure item)

github-actions · 2026-03-15T19:56:06Z

DOOML/lib/anf.ml

+        cond_
+    in
+    return ret
+  | Fun _ -> failwith "should be CC/LL first"


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T19:56:08Z

DOOML/lib/riscv.ml

+  | Etc of string
+[@@deriving variants]
+
+let todo () = failwith "todo"


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T19:56:08Z

DOOML/lib/riscv.ml

+open State
+
+let spf = Format.asprintf
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T19:56:08Z

DOOML/lib/riscv.ml

+        | ">=" -> [ slt rd rs1 rs2; xori rd rd 1 ]
+        | "=" -> [ sub (temp 0) rs1 rs2; seqz rd (temp 0) ]
+        | "<>" -> [ sub (temp 0) rs1 rs2; snez rd (temp 0) ]
+        | _ -> assert false


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T19:56:08Z

DOOML/lib/riscv.ml

+      in
+      let argc = List.length args in
+      (match arity with
+       | `Fun arity when arity == argc ->


No description provided.

github-actions · 2026-03-15T19:56:08Z

DOOML/lib/state.ml

@@ -0,0 +1,19 @@
+module M (S : sig


OCaml files should provide license information in second line (structure item)

github-actions

Zanuda-linter report

github-actions · 2026-03-15T20:07:11Z

DOOML/lib/fe.ml

@@ -0,0 +1,431 @@
+open Angstrom


File 'DOOML/lib/fe.ml' doesn't have corresponding .mli interface

github-actions · 2026-03-15T20:07:11Z

DOOML/bin/llvm.ml

+open DOOML
+module Map = Base.Map.Poly
+
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T20:07:11Z

DOOML/bin/riscv.ml

+open DOOML
+module Map = Base.Map.Poly
+
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T20:07:11Z

DOOML/lib/anf.ml

@@ -0,0 +1,427 @@
+type immexpr =


OCaml files should provide license information in second line (structure item)

github-actions · 2026-03-15T20:07:11Z

DOOML/lib/anf.ml

+        cond_
+    in
+    return ret
+  | Fun _ -> failwith "should be CC/LL first"


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T20:07:13Z

DOOML/lib/riscv.ml

+  | Etc of string
+[@@deriving variants]
+
+let todo () = failwith "todo"


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T20:07:13Z

DOOML/lib/riscv.ml

+open State
+
+let spf = Format.asprintf
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T20:07:13Z

DOOML/lib/riscv.ml

+        | ">=" -> [ slt rd rs1 rs2; xori rd rd 1 ]
+        | "=" -> [ sub (temp 0) rs1 rs2; seqz rd (temp 0) ]
+        | "<>" -> [ sub (temp 0) rs1 rs2; snez rd (temp 0) ]
+        | _ -> assert false


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-15T20:07:13Z

DOOML/lib/riscv.ml

+      in
+      let argc = List.length args in
+      (match arity with
+       | `Fun arity when arity == argc ->


No description provided.

github-actions · 2026-03-15T20:07:13Z

DOOML/lib/state.ml

@@ -0,0 +1,19 @@
+module M (S : sig


OCaml files should provide license information in second line (structure item)

github-actions · 2026-03-16T15:23:15Z

Документация и тестовое покрытие (75.88%) должны скоро появиться.

https://kakadu.github.io/comp25/docs/DOOML

https://kakadu.github.io/comp25/cov/DOOML

2026-03-16 18:23

Email	Commits	Files	Insertions	Deletions	Total Lines
ignat.sergeev@softcom.su	47	38	2627	1596	4223
belyaningeorge@ya.ru	11	41	3436	352	3788
-----	-------	-----	----------	---------	---------

github-actions

Zanuda-linter report

github-actions · 2026-03-16T15:24:12Z

DOOML/lib/llvm_wrapper.ml

@@ -0,0 +1,120 @@
+[@@@ocaml.text "/*"]


File 'DOOML/lib/llvm_wrapper.ml' doesn't have corresponding .mli interface

github-actions · 2026-03-16T15:24:12Z

DOOML/bin/llvm.ml

+open DOOML
+module Map = Base.Map.Poly
+
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-16T15:24:12Z

DOOML/bin/riscv.ml

+open DOOML
+module Map = Base.Map.Poly
+
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-16T15:24:12Z

DOOML/lib/anf.ml

+        cond_
+    in
+    return ret
+  | Fun _ -> failwith "should be CC/LL first"


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-16T15:24:12Z

DOOML/lib/codegen.ml

+
+open (val Llvm_wrapper.make context builder the_module)
+
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-16T15:24:13Z

DOOML/lib/ll.ml

+          ctx'.lifts, ctx', ast
+      in
+      ctx := reset ctx';
+      ctx := extend pattern !ctx |> snd;


Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable references and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.

github-actions · 2026-03-16T15:24:13Z

DOOML/lib/ll.ml

+          ctx'.lifts, ctx', ast
+      in
+      ctx := reset ctx';
+      ctx := extend pattern !ctx |> snd;


Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable references and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.

github-actions · 2026-03-16T15:24:13Z

DOOML/lib/riscv.ml

+  | Etc of string
+[@@deriving variants]
+
+let todo () = failwith "todo"


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-16T15:24:13Z

DOOML/lib/riscv.ml

+open State
+
+let spf = Format.asprintf
+let failf fmt = Format.kasprintf failwith fmt


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-16T15:24:13Z

DOOML/lib/riscv.ml

+        | ">=" -> [ slt rd rs1 rs2; xori rd rd 1 ]
+        | "=" -> [ sub (temp 0) rs1 rs2; seqz rd (temp 0) ]
+        | "<>" -> [ sub (temp 0) rs1 rs2; snez rd (temp 0) ]
+        | _ -> assert false


Using failwith (or assert false) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

github-actions · 2026-03-16T15:24:20Z

Linter report from 2026-03-16 18:24, for mini language DOOML

File '_build/default/lib/llvm_wrapper.ml' doesn't have corresponding .mli interface

File "bin/llvm.ml", line 8, characters 33-41:
8 | let failf fmt = Format.kasprintf failwith fmt
                                     ^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "bin/riscv.ml", line 8, characters 33-41:
8 | let failf fmt = Format.kasprintf failwith fmt
                                     ^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "lib/anf.ml", line 214, characters 13-21:
214 |   | Fun _ -> failwith "should be CC/LL first"
                   ^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "lib/codegen.ml", line 13, characters 33-41:
13 | let failf fmt = Format.kasprintf failwith fmt
                                      ^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "lib/codegen.ml", line 42, characters 9-21:
42 |   | _ -> assert false
              ^^^^^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "lib/codegen.ml", line 91, characters 47-59:
91 |   Map.merge_skewed ~combine:(fun ~key:_ _ _ -> assert false) rt binops
                                                    ^^^^^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "lib/fe.ml", line 179, characters 9-21:
179 |   | _ -> assert false
               ^^^^^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "lib/ll.ml", line 104, characters 7-10:
104 |       (ctx
             ^^^
Alert zanuda-linter: Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable `ref`erences and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.
File "lib/ll.ml", line 106, characters 39-42:
106 |           | Ast.Rec -> extend pattern !ctx |> snd
                                             ^^^
Alert zanuda-linter: Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable `ref`erences and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.
File "lib/ll.ml", line 107, characters 27-30:
107 |           | Ast.NonRec -> !ctx);
                                 ^^^
Alert zanuda-linter: Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable `ref`erences and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.
File "lib/ll.ml", line 111, characters 36-39:
111 |           let body, ctx' = ll body !ctx in
                                          ^^^
Alert zanuda-linter: Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable `ref`erences and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.
File "lib/ll.ml", line 114, characters 34-37:
114 |           let ast, ctx' = ll ast !ctx in
                                        ^^^
Alert zanuda-linter: Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable `ref`erences and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.
File "lib/ll.ml", line 117, characters 6-9:
117 |       ctx := reset ctx';
            ^^^
Alert zanuda-linter: Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable `ref`erences and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.
File "lib/ll.ml", line 118, characters 6-9:
118 |       ctx := extend pattern !ctx |> snd;
            ^^^
Alert zanuda-linter: Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable `ref`erences and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.
File "lib/ll.ml", line 118, characters 29-32:
118 |       ctx := extend pattern !ctx |> snd;
                                   ^^^
Alert zanuda-linter: Using mutable data structures for teaching purposes is usually discouraged. Replace Hashtables by standard tree-like maps or consider Hash-Array Mapped Tries (HAMT). Use mutable `ref`erences and mutable structure fields only if it is really required. In all places where it is needed indeed, describe in a comment why it is needed there.
File "lib/riscv.ml", line 277, characters 14-22:
277 | let todo () = failwith "todo"
                    ^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "lib/riscv.ml", line 424, characters 33-41:
424 | let failf fmt = Format.kasprintf failwith fmt
                                       ^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated
File "lib/riscv.ml", line 480, characters 15-27:
480 |         | _ -> assert false
                     ^^^^^^^^^^^^
Alert zanuda-linter: Using `failwith` (or `assert false`) usually is a clue that a corner case is not being handled properly. To report errors we recommend using error monad instead. In princliple, these construction are OK for temporary work-in-progress code, but in release they should be eliminated

Kakadu · 2026-03-16T17:33:08Z

Давайте сделаем вид, что тут всё достаточно хорошо для ТПшек.

georgiy-belyanin and others added 30 commits January 16, 2026 19:28

me: fix ANF of if-then-else

d3cc923

Previous implementation of the if-then-else ANF process was wrong. It actually executed both then and else branches and then chosen one of the results. This patch fixes it and now both branches are executed exclusively.

parser: not parse keywords as identifiers

be95b2f

This patch prevents the parser from handling the keywords as identifiers.

parser: support plugs, tuples, units

63fc9ec

This patch introduces plugs, tuples, and units into the parser. In other words, the following code can now be parsed properly. ```ocaml let () = _;; let _ = _;; let (a, b) = _;; ```

codegen

f2393ff

separate

fix builtin

8097cfc

fix function type lookup

21539ad

fix void call

4255794

formatted

17c267b

add basic test

293ca3a

rm unused comment

8c86231

fix function variables

7f88207

fix closure_apply

ccaacd2

emit binary

3fc57d2

disable llvm verbosity

b6fc30b

non rec support

7fdd7e1

rm unused open

c398da6

report error on multiple params with same name

784240c

add features to binary emition

01d55fe

fix codegen test

8f6a9a1

extra ffi non arch specific runtime

2c88ac1

specify riscv features

a879fa7

merge runtime files

ef9cbec

rm flake

6534ece

ignat.sergeev added 7 commits January 25, 2026 23:00

collect codegen

b49c17a

implement unit exprs

bcb0e79

finalize gc runtime

49aecf7

add gc status builtins

ad9c277

unbox int when printing debug info

54bb99a

add gc status builtins to middleend

bb052d6

mark fwd before copying args or fields (because we can)

ddad515

georgiy-belyanin force-pushed the dooml-basic branch 2 times, most recently from 8d3edd1 to f23b6c7 Compare January 26, 2026 11:59

General fixes for DOOML

b138e2c

Let's try to cleanup everything...

georgiy-belyanin force-pushed the dooml-basic branch from f23b6c7 to b138e2c Compare January 26, 2026 12:01

ignat.sergeev added 6 commits March 15, 2026 21:41

fix tests sources

afbd2d4

separate gc, non-gc runtime; fix gc bank overflow checks

323362d

collect only gc headers

8080f62

add integration tests

005a669

formatted

6552e64

Updated formatter version

cbca94f

IgnatSergeev force-pushed the dooml-basic branch from 7d81b41 to 719eb56 Compare March 15, 2026 19:47

github-actions bot reviewed Mar 15, 2026

View reviewed changes

github-actions bot added the TOO_MANY_LINTS label Mar 15, 2026

ci: fix build, tests

37222fb

IgnatSergeev force-pushed the dooml-basic branch from 719eb56 to 37222fb Compare March 15, 2026 19:56

github-actions bot reviewed Mar 15, 2026

View reviewed changes

fix zanuda linter

280856f

github-actions bot reviewed Mar 16, 2026

View reviewed changes

Kakadu marked this pull request as ready for review March 16, 2026 17:32

Kakadu merged commit fd1c917 into Kakadu:master Mar 16, 2026
2 checks passed


		open (val Llvm_wrapper.make context builder the_module)

		let failf fmt = Format.kasprintf failwith fmt

Conversation

georgiy-belyanin commented Jan 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Mar 16, 2026

Uh oh!

github-actions bot left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions bot Mar 16, 2026

Choose a reason for hiding this comment

georgiy-belyanin commented Jan 16, 2026 •

edited

Loading